home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.amiga.programmer
- Path: cs.vu.nl!irmen
- From: irmen@cs.vu.nl (Irmen de Jong)
- Subject: Dynamic loading/linking
- Nntp-Posting-Host: prauw.cs.vu.nl
- Sender: news@cs.vu.nl
- Organization: Dept. of Computer Science, Vrije Universiteit Amsterdam
- Date: Fri, 29 Mar 1996 10:00:38 GMT
- X-Newsreader: TIN [UNIX 1.3 950824BETA PL0]
- Message-ID: <Dp0x52.90C.0.-s@cs.vu.nl>
-
- Say I want to split my program into separate parts (because it's
- getting too big, or because some parts are rarely used).
- (I'm talking about my port of the python interpreter here)
-
- What solutions are feasible?
-
- - Overlay. Don't know how this works. Can overlays reference global
- data? Can overlays be loaded without replacing other parts of the
- program? Can overlays be constructed without a great deal of work
- required by the programmer (yea, that's right, me)?
-
- - Amiga shared library. Would be most ideal, but libraries cannot reference
- global data. (Ok Ok they can by passing all the pointers to all the
- global data you want to reference but in my case this is no option.
- Way to much global data.)
-
- - Dynamic loading with LoadSeg(). Can't reference global data, can I?
- See shared library.
-
- *sigh* I thought it wasn't necessary but now I think the Amiga should have
- some sort of dynamic linking support. AmigaDOS 4.0?
-
-
- (Examples of programs getting too big: Pagestream 3 and Imagine 3.0+, both
- well over 1 megabyte main executable, of which big parts are used
- very infrequently, I reckon)
-
- --
- / Irmen de Jong (email: irmen@cs.vu.nl WWW: http://www.cs.vu.nl/~irmen/) \
- \ Computer Science, VU A'dam, NL. ``Nothing lasts forever'' -- Species /
-